BeAIM Bugs, Issues, and Missing Features

Here are the problems I know about: (I probably missed a few, though.)


General:

1.  There is no way to log off, other than closing the program. There is a menu option for this, but it's disabled since it doesn't work yet.

2.  Some of the menus are blank, or their options don't work. Hey, I wanted to get something working before I fiddled with details.   :-)

3.  Occasionally, users I've been chatting with (who were not using BeAIM at the time) reported getting messages like this:
Previous message was not received by SuccUBus42 because of error<!-- (8:30:52 PM)-->: []A[][]*P
Ummmm..... I'm a bit confused as to why this is happening. For the moment I'm writing it off as an error of AOL's servers, but we'll see.

4.  BeAIM does not report whether or not you are idle... you will always appear active to other users.

5.  None of AOL Instant Messenger's 2.0 features are supported yet.

The Sign On window:

1.  The Password text edit control doesn't work like it should. This is not one of my major worries at the moment.

2.  If you press the cancel button while it is in the connecting phase, often it will lock up BeAIM when you try and reconnect or close the program. Workaround: don't cancel if it's not connected and sending/receiving data.


The Buddy List window:

1.  When switching workspaces, the top of the Buddy List tab tends to suddenly go offscreen. I'm working on it.


The Chat window:

1.  The Show Font Colors/Sizes option is only active for incoming data... one you enable it, all NEW messages will be shown in a plain font. The old ones will stay the way they are... unreadable or not.

2.  Occasionally, the Chat Window has crashed BeAIM when a new message comes in... I think I might have nailed this, but it was so difficult to duplicate that I don't know for sure. You've been warned.


The Info window:

1.  Not sure about this, but the "Online Time" field may be incorrect based on your time zone settings, and how far off your system clock is as opposed to the AIM Server's clock. I'm going to code in a time correction routine for this in a future release, but for now just use your best judgment to figure out the correct value.

